Configuration File to Customize the Standard Custom Fingerprint Caching
Since the 8.2.x release, fingerprint caching was allowed to improve the performance while loading standalone licenses (it reduced the load time typically when fingerprints—such as IP address, disk ID, host name, Ethernet address, computer ID key, and hard disk serial number—were used). However, this default caching conflicted with the standard custom locking when fingerprint values changed dynamically.
To overcome this, since the 8.3.0 release (Windows) and 8.4.1 release (UNIX), you can use a configuration file to set the standard custom fingerprint caching as ON or OFF.
The table below summarizes the default caching settings for the various locking criteria:
| Locking Option | Default Fingerprint Caching (ON\OFF) | Caching Customization Option Provided? |
|---|---|---|
|
>IP address >Disk ID >Host name >Ethernet address >Computer ID key >Hard disk serial number >ID PROM |
ON |
No. You cannot disallow the default caching setting. |
| Standard Custom | ON |
Yes. Using the configuration file (as described in this topic). You are recommended to disable caching using the configuration file in case of multiple standard custom criteria or when these change dynamically. For example, if license 1 is locked on UID 1 and license 2 is locked UID 2, you should use the configuration file to disable caching. Else, the first fingerprint retrieved will be cached. |
| Extended Custom | OFF |
No. You can implement your own caching mechanism as described in the custexlock sample (available for both Windows and UNIX) |
Configuration File for Customizing Standard Custom
The configuration file can have the MACHINEIDCACHE section with the key-value pairs for CustomLockCachingOff.
Where,
>Setting the value of CustomLockCachingOff key as 1 and 0, turns off and on the caching of standard custom lock fingerprint, respectively.
>Setting the value other than 0 or 1 turns on the caching.
For example, see a sample configuration file snippet:
----------------------------
[MACHINEIDCACHE]
CustomLockCachingOff 0
----------------------------Setting the value 0 above, for the CustomLockCachingOff key, turns on the caching of custom lock fingerprint
Calling the VLSsetFileName API to Integrate the Configuration File
The API, VLSsetFileName, is also enhanced to read the configuration file (see ). The new value is VLS_GENERICCONF added to the enum VLS_FILE_TYPE defined in lserv.h.
For example, calling the above API as below:
VLSsetFileName(VLS_GENERICCONF, "GenericConfig", NULL, NULL);
This means that a configuration file named "GenericConfig" is to be read by the client library from the application directory.
The fingerprints will be cached under the following scenarios:
>When the configuration file is not set using the API VLSsetFileName.
>When the configuration file is set, but does not exist.
>When the configuration file exists, but the required section is not present.
>When the configuration file and the required section exist, but the required key is not present in that section.